Copied from Kent email of June 6.

Just so it's captured somewhere, here's my procedure for building a new SIAM tag while the service is running.

Check Out

• login as ops
• cd /home/ops/build
• . /home/ops/scripts/setCVSROOT <cvs user> [note: source siam-env; note the dot]
• /home/ops/scripts/minimalCheckout <cvs user> <siam-tag> [note: this takes a long time]
• mv /home/ops/build/siam2 /home/ops/build/siam2<siam-tag>- Now done by minimalCheckout

Make

• . /home/ops/scripts/siam-env /home/ops/build/<siam-tag> [note: source siam-env; note the dot]
• cd /home/ops/build/<siam-tag>
• mkdir classes if it doesn't exist
• make -s [note: this takes 20\-30 min, you'll only see errors and warnings \(there are many harmless warnings\)]
• make siamjar 
• cd /native/foce
• make foceio
• make testSensoray
• cd /home/ops/build/siam2-<siam-tag>
• cvs -Q co puckxml
• mkdir ports if it doesn't exist
• make focepucks (note: 1731.xml is missing; I've been copying junk.xml to 1731.xml)
• cp properties/siamPort.cfg.foce properties/siamPort.cfg

To install:

• exitNode loc
• cp /home/ops/siam2 /home/ops/siam2-<oldSiamTag>
• mv /home/ops/build/siam2-<siam-tag> /home/ops/siam2